OCV vs. SOC curve configuration improvements #77
Conversation
This avoids having OCV and SOC arrays with all zeros exposed to the user via ThingSet. The curves can be initialized with default values for a certain cell and afterwards be customized.
Instead, the pre-populated typical values for certain chemistries should be adjusted to avoid having totally invalid configurations (e.g. SOC lookup tables with 0 V)
There was a problem hiding this comment.
I tested this change on v0.4.1 hardware and it works as expected.
To set the OCV/SoC arrays via the USB-C shell, ensure CONFIG_SHELL_BACKEND_SERIAL_RX_RING_BUFFER_SIZE=256 is configured; otherwise, the warning W: RX ring buffer full will occur, and the new values won’t be applied. Should this generally be increased, or should it work via the serial console using connector J6 as described here?
What I tested (leaving this note here for anyone searching for this information):
thingset !Conf/xPresetLFP [45]fills the OCV/SoC values for LFP.thingset =Conf {\"sOcvPoints_V\" :[3.392,3.314,3.309,3.308,3.304,3.296,3.283,3.275,3.271,3.268,3.265,3.264,3.262,3.252,3.240,3.226,3.213,3.190,3.177,3.132,2.8]}changes the last value from2.833to2.8and it works.
|
Thanks for testing. I've only tested writing using the Android app via Bluetooth (I'm about to finally publish it in the Play store...) and afterwards checked the values on the shell. Looks like I should have tested writing on the shell as well ;) It makes sense to increase the buffer size. Will add a commit, probably on Monday. |
Previously, only a pre-selected OCV vs. SOC curve for different cells could be selected, but the curve was not exposed via ThingSet. For the custom cell, every value had to be configured manually.
With the new approach, the custom cell is removed and instead the actual cell configuration can be pre-set with default values for different cell types. These actual values are now also exposed via ThingSet and can be adjusted as well.